home *** CD-ROM | disk | FTP | other *** search
- DOCUMENTATION FOR THE PROGRAM CLIP.COM
-
- If you were to execute CLIP at the DOS prompt without giving it any parameters
- this is what you would see:
-
-
- CLIP Copyright (C) 1987 by Charles Lazo III, v1.23
-
- CLIP syntax: CLIP [d:][path]filename.ext
-
- CLIP removes all terminal ^Z's, RETURN's and LINEFEEDS's from the file.
-
- CLIP.COM is shareware with a cost of $2 to satisfied users.
-
- You may send payment, suggestions for improvement, complaints, bug reports, et
- cetera to:
- Charles Lazo III
- P.O. Box 2312
- Hohenwald, TN 38462.
-
-
-
-
-
- As can be seen valid parameters for the CLIP program are:
-
- [d:][path]filename.ext
-
- where [d:] means you can use an optional drive letter (floppy, hard disk, ram
- disk, etc.) [path] means that you can specify any valid path name for the file
- represented here by filename.ext.
-
- The object of CLIP is to remove any terminating ^Z's, RETURN's and LINEFEED's
- from the specified file. These are characters with ASCII codes 26, 13, and 10
- respectively or in hexadecimal 1A, D, and A. Writing this program was motivated
- by the BRIEF (tm) editor which places these characters at the end of a file
- without regard to the user's wishes. Perhaps the only problem these additions
- may cause is the doubling of DOS prompts at the completion of batch files.
- However, CLIP may be customized with DEBUG to eliminate null's (ASCII 0) or any
- other desired character(s) from the end of files.
-
- To do this place a copy of CLIP.COM in the same directory as a copy of DEBUG.COM
- and enter DEBUG CLIP.COM at the DOS prompt. Then to see the table of ASCII
- values that CLIP will eliminate from the end of files enter this:
-
- d 400 l 100
-
- You should see your screen fill with a table that looks like this:
-
- xxxx:0400 00 00 00 00 00 00 00 00-00 00 01 00 00 01 00 00 ................
- xxxx:0410 00 00 00 00 00 00 00 00-00 00 01 00 00 00 00 00 ................
- xxxx:0420 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:0430 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:0440 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:0450 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:0460 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:0470 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:0480 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:0490 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:04A0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:04B0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:04C0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:04D0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:04E0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
- xxxx:04F0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
-
- Every character that is eliminated from the end of a file by CLIP will have a
- non zero value in the table (in this example the positions 40A, 40D, and 41A
- are occupied by 01 and this is the default setup for CLIP that eliminates
- LINEFEEDS, RETURNS's, and ^Z from the ends of files). Every character that is
- not eliminated from the end of files by CLIP will have its corresponding
- location in the table occupied by 00. The xxxx entries on the left of the
- table indicate a four digit hexadecimal number that will vary depending on your
- computer's setup.
-
- To change the characters eliminated from the end of a file by CLIP you must
- modify this table in the CLIP.COM file to indicate the characters of your
- choice. For example to patch CLIP.COM so that only null's will be eliminated
- from the ends of your files you should type in the following at DEBUG's "-"
- prompt:
-
- -e40a
-
- xxxx:040A 01.0
-
- -e40d
-
- xxxx:040D 01.0
-
- -e41a
-
- xxxx:041A 01.0
-
- -e400
-
- xxxx:0400 00.1
-
- -w
-
- -q
-
- Note: DEBUG's responses are the lines that begin with xxxx, except that you
- must type the 0 or 1 at the end of the line. Provided you have a version of
- CLIP that contains the default setting as shown in the table above, these
- commands to DEBUG will write the file CLIP.COM to your disk that will remove
- only null's from the end of input files and you will be returned to the DOS
- prompt.
-
- You need not make the non zero values in the table all 1's for indicating
- characters to be removed from files; any non zero value will do.
-
- CLIP will not work on files that are larger than 65535 bytes (64K - 1). Nor
- will it work if available memory is less than the file's size.
-
- If you were to attempt to CLIP a file that had none of the excludable characters
- at its end, then CLIP would open the file, notice this condition, close the
- file, and exit without changing the file in any way (in particular date and
- time of creation of the file would be preserved).
-
- CLIP exits with an extensive list of return codes that describe any error
- conditions that may apply. The DOS related error codes and a paraphrase of the
- error messages returned by CLIP are:
-
- 2 file not found.
- 3 path not found.
- 4 no handle available; all in use.
- 5 access denied.
- 8 insufficient memory.
-
- Other possible (but highly improbable) DOS error codes can be returned. They
- are documented in the DOS technical reference. The ones above form a subset of
- this group. If an error of this type ever does occur, then it will be reported
- as for example:
-
- CLIP error: unexpected error (code 0F).
-
- If any error of this type is ever encountered by a user, then I would like to
- know; it will be accounted for in any update of CLIP.
-
- CLIP also returns some error codes of its own these are:
-
- 129 Not an error actually, but the code returned by CLIP when no parameters
- are entered for CLIP and the message as shown at the beginning of this
- documentation is displayed.
-
- 130 The file is too large to CLIP, i.e., over 65535 bytes in length.
-
- 131 If this error ever occurs CLIP will respond with:
-
- CLIP error: file not written: disk full?
-
- This error is highly unlikely since by my own test on a full floppy disk
- the file that CLIP wrote occupied the same disk region as the original file.
-
- If no error is detected and CLIP carries out the operation successfully, then
- the error code returned will be 0 and CLIP will finish after displaying the
- copyright message.
-
- As the owner of the copyright of this software it is my wish that CLIP may be
- freely copied and distributed, subject to the provision that this document file
- CLIP.DOC accompany the CLIP.COM program. Although not a provision of the
- copyright, it would probably be best if the CLIP.COM file were distributed in
- its original form, so that it acts in accordance with the message displayed
- when CLIP is entered without any parameters.
-
- Although I am interested in the comments of anyone concerning this program,
- the comments that will receive the greatest consideration will be those given
- by users who send me the $2 payment for use of it.
-
- The program may be enhanced in a number of ways. Some which I have thought of
- are:
-
- use with files over 65535 bytes in length
- use with files larger than available memory
- use of the wild card characters * and ? in file name specification
- allowing the specification of excludable characters on the command line
-
- If you wish to vote for any of these features or others, then your vote will
- be tallied if you send in the $2 payment. I will attempt to implement the most
- favored feature(s) in any future release.
-
- DISCLAIMER
-
- This software CLIP.COM and the accompanying documentation CLIP.DOC are not
- warranted for any purpose either expressed or implied including but not
- limited to merchantability or fitness of purpose. By using the software you
- agree to this.
-
- If you wish to contact me you may do so by writing to the address at the top
- of this document or by using my CompuServe (tm) user ID 72210,17.
-
- Ma Bell knows me as 615/796-2640.
-
- bye
-
-
-
- ----------------end-of-author's-documentation---------------
-
- Software Library Information:
-
- This disk copy provided as a service of
-
- The Public (Software) Library
-
- Disks in the library are updated monthly.
- For a copy of the latest monthly software library newsletter
- and a list of the 800+ disks in the library, call or write
-
- The Public (Software) Library
- P.O.Box 35705 K
- Houston, TX 77235-5705
- (713) 721-6104
-
- We are not the authors of this program, nor are we associated
- with the author in any way other than as a distributor of the
- program in accordance with the author's terms of distribution.
-
- Please direct shareware payments and specific questions about
- this program to the author of the program, whose name appears
- elsewhere in this documentation. If you have trouble getting
- in touch with the author, we will do whatever we can to help
- you with your questions. All programs have been tested and do
- run. To report problems, please use the form that is in the
- file PROBLEM.DOC on many of our disks or in other written for-
- mat with screen printouts, if possible.
-